fix: use >= version constraints for action deps to enable Dependabot updates#419
fix: use >= version constraints for action deps to enable Dependabot updates#419
>= version constraints for action deps to enable Dependabot updates#419Conversation
…mp cpp-linter to 1.12.1 Agent-Logs-Url: https://github.com/cpp-linter/cpp-linter-action/sessions/b460992a-13de-459d-beaf-8758cb4812f7 Co-authored-by: shenxianpeng <3353385+shenxianpeng@users.noreply.github.com>
>= version constraints for action deps to enable Dependabot updates
Cpp-Linter Report
|
|
We switched to exact version requirements for a few reasons. I didn't think dependabot errors is a good reason to revert that decision. I suspect the uv.lock errors are more likely from still supporting python 3.9, but that should be resolved by #420 FYI, the recommended version of pygments in security alert #11 has other bugs that need to be resolved first before we upgrade pygments. |
cpp-linterandclang-toolswere pinned with exact==constraints in theactiondependency group, causing Dependabot to report "No update possible" —uv lock --upgrade-packagecannot change the lockfile when the specifier only allows one exact version.Changes
pyproject.toml: Changeactiongroup deps from exact (==) to minimum-version (>=) constraints, consistent withdev/docsgroups. The lockfile still pins the runtime version precisely.uv.lock: Regenerated withuv lock --upgrade-package cpp-linter, bumpingcpp-linterto1.12.1for Python ≥ 3.10 (stays at1.12.0for Python < 3.10, as1.12.1transitively requirespygit2 ≥ 1.19.2which dropped 3.9 support).